IBM Books

AIS V3.3 Protocol Config Ref Vol 1


Configuring and Monitoring BGP4

This chapter describes the BGP configuring and monitoring commands and includes the following sections:


Accessing the BGP4 Configuration Environment

To access the BGP configuration environment, enter the following command at the Config> prompt:

  Config> Protocol BGP
  BGP Config>

BGP4 Configuration Commands

This section describes the BGP configuration commands. These commands allow you to modify the BGP protocol behavior to meet your specific requirements. Some amount of configuration is necessary to produce a fully functional BGP router. Enter BGP configuration commands at the BGP config> prompt.

Table 25. BGP Configuration Command Summary
 Command   Function 
? (Help) Displays all the commands available for this command level or lists the options for specific commands (if available). See "Getting Help".
 Add   Add BGP neighbors and policies. 
 Attach   Attaches receive and send policy-list to a particular neighbor. 
 Change   Modifies information that was originally entered with the add command. 
 Delete   Deletes BGP configuration information that had been entered with the add command. 
 Disable   Disables certain BGP features that have been turned on by the enable command. 
 Enable   Enables BGP speakers, BGP neighbors or Classless BGP. 
 List   Displays BGP configuration items. 
 Move   Changes the order in which policies and aggregates are defined. 
 Set   Sets the IP-route-table-scan-timer. 
 Update   Manipulates a policy in a configured policy-list name using the submenu add, delete, change and move commands. 
Exit Returns you to the previous command level. See "Exiting a Lower Level Environment".

Add

Use the add command to add BGP information to your configuration.

Syntax:

add
aggregate . . .
neighbor . . .
no-receive asnum . . .
originate-policy . . .
policy-list . . .
receive-policy . . .
send-policy. . .

aggregate network prefix network mask
The add aggregate command causes the BGP speaker to aggregate a block of addresses, and advertise a single route to its BGP neighbors. You must specify the network prefix common to all the routes being aggregated and its mask. The following example illustrates how to aggregate a block of addresses from 194.10.16.0 through 194.10.31.255.

  1. The Network Prefix is the addresses being affected. The prefix is the first address in a range of addresses specified in a BGP policy.
    Valid Values: Any valid IP address.
    Default Value: none

  2. The Network Mask applies to the address specified in Network Prefix to generate an address used in a BGP policy.
    Valid Values: Any valid IP address.
    Default Value: none

Example:
add aggregate
Network Prefix [0.0.0.0]? 194.10.16.0
Network Mask [0.0.0.0]? 255.255.240.0

When you add an aggregate definition, remember to define a policy to block the aggregated routes from being exported. If you do not, the router will advertise both the individual routes and the aggregate you have defined. This does not apply when you are aggregating the routes, which are originated from it's IGP routing table.

neighbor neighbor IP address as# init timer connect timer hold timer keep alive timer tcp segment size

Use the add neighbor command to define a BGP neighbor. The neighbor can be internal to the BGP speaker's AS, or external. To activate this neighbor dynamically use the reset neighbor command from BGP monitoring.

  1. The IP address is the address of the neighbor you wish to peer with. It could be within your own autonomous system or in another autonomous system. If it is an external neighbor, both BGP speakers must share the same network. There is no such restriction for internal neighbors. The address has:
    Valid Values: Any valid IP address.
    Default Value: none

  2. The AS number is your own autonomous system number for internal neighbor or neighbor's autonomous system number. The AS number of the neighbor has:
    Valid Values: An integer in the range of 0 - 65535
    Default Value: none

  3. The Init timer to specifies the amount of time the BGP speaker waits to initialize resources and reinitiate transport connection with the neighbor in case the speaker has previously changed to IDLE state due to an error. If the error persists, this timer increases exponentially.
    Valid Values: 0 to 65535 seconds.
    Default Value: 12 seconds

  4. The Connect timer specifies the amount of time the BGP speaker waits to reinitiate transport connection to its neighbor, if the TCP connection fails while in either CONNECT or ACTIVE state. In the mean time, the BGP speaker continues to listen for any connection that may be initiated by its neighbor.
    Valid Values: 0 to 65535 seconds.
    Default Value: 120 seconds

  5. Enter the Hold timer to specify the length of time the BGP speaker waits before assuming that the neighbor is unreachable. Both neighbors exchange the configured information in OPEN message and choose the smaller of the two timers as their negotiated Hold Timer value.

    Once neighbors have established BGP connection, they exchange Keepalive messages at frequent intervals to ensure that the connection is still alive and the neighbors are reachable. The Keep-Alive timer interval is calculated to be one-third of the negotiated hold timer value. Hence the hold timer value must be either zero or at least three seconds.

    Note that on switched lines, you may wish to have the Hold Timer value of zero to save bandwidth by not sending Keepalives at frequent intervals.

    Valid Values: 0 to 65535 seconds.
    Default Value: 90 seconds

  6. The TCP segment size specifies the maximum data size that may be exchanged on the TCP connection with a neighbor. This value is used for active TCP connection with the neighbor.
    Valid Values: 0 to 65535 bytes.
    Default Value: 1024 bytes

Example:
add neighbor
Neighbor address [0.0.0.0]? 192.0.251.165
AS [0]? 165
Init timer [12]?
Connect timer [120]?
Hold timer [90]?
TCP segment size [1024]?

no-receive asnum
Use the add no-receive asnum to exclude AS-paths if the particular AS number appears anywhere inside the AS-path list.

The AS number has:

Valid Values: 0 to 65535
Default Value: none

Example:
add no-receive
Enter AS: [0]? 178

originate-policy (exclusive/ inclusive) network prefix network mask address match (Exact/Range) tag

Use the add originate-policy command to create a policy that determines whether a specific address, or range of addresses, can be imported to the BGP speaker's routing table from the IGP routing table.

Exclusive
Exclusive policies prevent route information from being included in the BGP speaker's routing table.

Inclusive
Inclusive policies ensure that specific routes will be included in the BGP speaker's routing table.

Network prefix
The network prefix for the addresses being affected.

Address match
The address, or range of addresses, that will be affected by the policy statement.

Tag
The value that has been set for a particular AS. All tag values match that of the AS from which they were learned.

Exclusive policies prevent route information from being included in the BGP speaker's routing table.

  1. The Network Prefix is the addresses being affected.
    Valid Values: Any valid IP address.
    Default Value: none

  2. Enter the Network Mask to be applied to the address specified in Network Prefix to generate an address used in a BGP policy.
    Valid Values: Any valid IP address.
    Default Value: none

  3. Select whether the Address match is to be a range of addresses or an exact address.

  4. A TAG is the value that has been set for a particular AS. Tag values match that of the AS from which they were learned.
    Valid Values: 0 to 65535
    Default Value: none

The following example includes all routes in the BGP speaker's IGP routing table to be advertised.

Example:
add originate-policy exclusive
Network Prefix [0.0.0.0]?
Network Mask [0.0.0.0]?
Address Match (Exact/Range) [Exact]? range
Tag [0]?

See "Originate Policy Examples" for detailed examples of this policy command.

policy-list
Use the add policy-list command to configure a group of policy, which can be attached to a specific neighbor using the attach policy-to-neighbor command.

Example: add policy-list

Name[]? nbr1-rcv
Policy Type(Receive/Send)[Receive]?Receive

Example: add policy-list

Name[]? nbr1-snd
Policy Type(Receive/Send)[Receive]?Send
Note:See "Neighbor Based Receive Policy Examples" and "Neighbor Based Send Policy Examples" for detailed examples of this policy command.

receive-policy (exclusive/ inclusive) network prefix network mask address match originating as# adjacent as# igpmetric (inclusive only)

Use the add receive-policy command to determine what routes will be imported to the BGP speaker's routing table.

Exclusive policies prevent route information from being included in the BGP speaker's routing table.

  1. The Network Prefix is the addresses being affected.
    Valid Values: Any valid IP address.
    Default Value: none

  2. The Network Mask applies to the address specified in Network Prefix to generate an address used in a BGP policy.
    Valid Values: Any valid IP mask.
    Default Value: none

  3. The Address match is a range of addresses or an exact address.

  4. An Originating AS# has:
    Valid Values: 0 to 65535
    Default Value: none

  5. The Adjacent AS# to specifies the neighboring AS number.

    Valid Values: 0 to 65535
    Default Value: none

Example:
add receive-policy exclusive
Network Prefix [0.0.0.0]? 10.0.0.0
Network Mask [0.0.0.0]?  255.0.0.0
Address Match (Exact/Range) [Exact]? range
Originating AS# [0]? 168
Adjacent AS# [0]? 165

See "AS Based Receive Policy Examples" for detailed examples of this policy command.

send-policy (exclusive/ inclusive) network prefix network mask address match tag adjacent as#

Use the add send-policy command to create policies that determine which of the BGP speaker's learned routes will be readvertised. These routes could be internal or external to the BGP speaker's AS.

Exclusive policies prevent route information from being included in the BGP speaker's routing table.

  1. The Network Prefix is for the addresses being affected.
    Valid Values: Any valid IP address.
    Default Value: none

  2. The Network Mask applies to the address specified in Network Prefix to generate an address used in a BGP policy.
    Valid Values: Any valid IP address.
    Default Value: none

  3. The Address match is a range of addresses or an exact address.

  4. A TAG. is the value that has been set for a particular AS. Tag values match that of the AS from which they were learned.
    Valid Values: 0 to 65535
    Default Value: none

  5. The Adjacent AS# specifies the neighboring AS number.
    Valid Values: 0 to 65535
    Default Value: none

Example:
add send exclusive
Network Prefix [0.0.0.0]? 180.220.0.0
Network Mask [0.0.0.0]? 255.255.0.0
Address Match (Exact/Range) [Exact]? range
Tag [0]?
Adjacent AS# [0]? 25

See "AS based Send Policy Examples" for detailed examples of this policy command.

Attach

Use the attach policy-to-neighbor command to attach a configured policy-list name to a specific neighbor. You can attach up to three receive and three send policy-list names.

Syntax:

attach
policy-to-neighbor

Example: attach policy-to-neighbor

Neighbor address [0.0.0.0]? 192.0.251.165
First receive policy list name (none for global AS based policy)[]? nbr1-rcv
Second receive policy list name (none for exit)[]? 
First send policy list name (none for global AS based policy)[]? nbr1-snd
Second send policy list name (none for exit)[]?
 
Note:See "Neighbor Based Receive Policy Examples" and Neighbor Based Send Policy Examples for detailed examples of this policy command.

Change

Use the change command to change a BGP configuration item previously installed by the add command.

Syntax:

change
aggregate . . .

neighbor . . .

originate-policy . . .

policy-to-neighbor

receive-policy . . .

send-policy. . .

aggregate index# network prefix network mask
This example changes the current aggregate (aggregate 1). The change causes aggregate 1 to use a different network prefix and mask to aggregate all routes in the address range from 128.185.0.0 to 128.185.255.255.
Example:
change aggregate 1
Network Prefix [128.185.0.0]? 128.128.0.0
Network Mask [255.255.0.0]? 255.192.0.0

neighbor neighbor IP address as# init timer connect timer hold timer keep alive timer tcp segment size
The following example changes the value of the hold timer to zero for neighbor 192.0.251.165.

The neighbor address to be modified has:

Valid Values: Any valid IP address.
Default Value: none

To reactivate this neighbor dynamically use the reset neighbor command from BGP monitoring.

Example:
change neighbor 192.0.251.165
AS [165]?
Init timer [12]?
Connect timer [60]?
Hold timer [12]? 0
TCP segment size [1024]?

originate-policy index# (exclusive/ inclusive) network prefix network mask address match tag
Use the change originate-policy command to alter an existing originate policy definition.

This example alters the BGP speaker's originate policy. Rather than excluding networks with prefix 194.10.16.0 from the IGP routing table, the policy will now include all routes.

Example:
change originate-policy
Enter index of originate-policy to be modified [1]?
Policy Type (Inclusive/Exclusive) [Exclusive]? inclusive
Network Prefix [194.10.16.0]? 0.0.0.0
Network Mask [255.255.240.0]? 0.0.0.0
Address Match (Exact/Range) [Range]?
Tag [0]?

policy-to-neighbor
Use the change policy-to-neighbor command to change a policy-list attachment to a particular neighbor.
Example:
change policy-to-neighbor
Neighbor address [0.0.0.0]? 192.0.251.165
First receive policy list name to be changed[nbr1-rcv]? 
Second receive policy list name to be changed[]?
Third receive policy list name to be changed[]?
First send policy list name to be changed[nbr1-snd]? 
Second send policy list name to be changed[]?
Third send policy list name to be changed[]?

receive-policy index# (exclusive/inclusive) network prefix network mask address match originating as# adjacent as# igpmetric (inclusive only)
Use the change receive-policy command to alter an existing receive policy definition.

This example adds a restriction to the BGP speaker's receive-policy. Rather than import route information from every BGP peer into its IGP routing table, it will now prevent routes from AS 165 from being imported.

Example:
change receive-policy
Enter index of receive-policy to be modified [1]?
Policy Type (Inclusive/Exclusive) [Inclusive]? exclusive
Network Prefix [0.0.0.0]?
Network Mask [0.0.0.0]?
Address Match (Exact/Range) [Range]?
Originating AS# [0]?
Adjacent AS# [0]? 165

send-policy index# (exclusive/ inclusive) network prefix network mask address match tag adjacent as#
Use the change send-policy command to alter an existing send policy to one that is more inclusive, or more exclusive.

This example adds a restriction to the BGP speaker's send policy. The restriction ensures that all routes in the address range 194.10.16.0 to 194.10.31.255 will be excluded when advertising to autonomous system 165.

Example:
change send-policy
Enter index of send-policy to be modified [1]?
Policy Type (Inclusive/Exclusive) [Inclusive]? exclusive
Network Prefix [0.0.0.0]? 194.10.16.0
Network Mask [0.0.0.0]? 255.255.240.0
Address Match (Exact/Range) [Range]?
Tag [0]?
Adjacent AS# [0]? 165

Delete

Use the delete command to delete a BGP configuration item previously installed by the add command.

Syntax:

delete
aggregate . . .

neighbor . . .

no-receive . . .

originate-policy . . .

policy-list . . .

policy-to-neighbor

receive-policy . . .

send-policy. . .

aggregate index#
You must specify the index number of the aggregate you want to delete. The index number is equivalent to the AS number.

Example: delete aggregate 1

neighbor neighbor IP address
Use this command to delete a BGP neighbor. You must specify the neighbor's network address.

The neighbor's network address to be deleted has:

Valid Values: Any valid IP address.
Default Value: none

To deactivate this neighbor dynamically use the reset neighbor command from BGP monitoring.

Example: delete neighbor 192.0.251.165

no-receive as
Use this command to delete the no-receive policy set up for a particular AS. You must specify the AS number.

The AS number has:

Valid Values: 0 to 65535
Default Value: none

Example: delete no-receive 168

originate-policy index#
Use this command to delete a specific originate policy. You must specify the index number associated with the policy.

Example: delete originate-policy 2

policy-list
Use the delete policy-list command to delete a policy-list.

Example: delete policy-list

Name of policy-list to delete []? nbr1-rcv
All policies defined for 'nbr1-rcv' will be deleted.
Are you sure you want to delete (Yes or [No]? Yes
Policy-list 'nbr1-rcv' is deleted. 

The policy-to-neighbor attachment will be adjusted accordingly.

policy-to-neighbor
Use the delete policy-to-neighbor command to delete an existing policy-list name attachment to a particular neighbor.

Example: delete policy-to-neighbor

Neighbor address [192.0.251.165]?
Remove first receive policy-list name [nbr1-rcv]
Are you sure you want to remove (Yes or [No])? yes
Remove first send policy-list name [nbr1-snd]
Are you sure you want to remove (Yes or [No])? yes   

receive-policy index#
Use this command to delete a specific receive policy. You must specify the index number associated with the policy.

Example: delete receive-policy

Enter index of receive-policy to be deleted [1]?

send-policy index#
Use this command to delete a specific send policy. You must specify the index number associated with the policy.

Example: delete send-policy 4

Disable

Use the disable command to disable a previously enabled BGP neighbor or speaker. Note that neighbors are implicitly enabled whenever added with the add command.

Syntax:

disable
BGP speaker

classless-bgp

compare-med-from-diff-AS

neighbor . . .

bgp speaker
Use the disable bgp speaker command to disable the BGP protocol.

Example: disable bgp speaker

classless-bgp
Use this command to disable a classless route for advertisement.

Example: disable classless-bgp
Note:Be sure that the patch bgp-subnets command is disabled.

compare-med-from-diff-AS
Use this command to disable a MED comparison between different ASs.

Example: disable compare-med-from-diff-AS

neighbor neighbor IP address
The neighbor address has:

Valid Values: Any valid IP address.
Default Value: none

Example: disable neighbor 192.0.190.178

Enable

Use the enable command to activate the BGP features, capabilities, and information added to your BGP configuration.

Syntax:

enable
BGP speaker

classless-bgp

compare-med-from-diff-AS

neighbor . . .

bgp speaker as# tcp segment size
Use the enable bgp speaker command to enable the BGP protocol.

Note: IBM only supports the latest version of BGP - BGP4, which is defined in RFC 1654.

  1. The AS number is associated with this collection of routers and nodes.
    Valid Values: 0 to 65535
    Default Value: none

  2. Enter the TCP segment size to specify the maximum segment size that BGP should use for passive TCP connections.
    Valid Values: 0 to 65535 bytes.
    Default Value: 1024 bytes
Example:
enable bgp speaker
AS [0]? 165
TCP segment size [1024]?

classless-bgp neighbor
Use this command to enable a classless route for advertisement.

Example: enable classless-bgp

compare-med-from-diff-AS
Use this command to enable MED comparison between different ASs.

Example: enable compare-med-from-diff-AS

neighbor neighbor IP address
Use this command to enable a BGP neighbor.

The neighbor address has:

Valid Values: Any valid IP address.
Default Value: none

Example: enable neighbor 192.0.190.178

List

Use the list command to display various pieces of the BGP configuration data, depending on the particular subcommand invoked.

Syntax:

list
aggregate

all

BGP speaker

neighbor

no-receive

originate-policy

policy-list . . .

policy-to-neighbor

receive-policy

send-policy

aggregate
Use the list aggregate command to all aggregated routes defined with the add aggregate command.

Example: list aggregate

Aggregation:
Index    Prefix               Mask
1         194.10.16.0        255.255.240.0

all
Use the list all command to list the BGP neighbors, policies, aggregated routes, and no-receive-as records in the current BGP configuration.

Example: list all

                   BGP Protocol:          Enabled
                   AS:                    167
                   TCP-Segment Size:      1024
                   Neighbors and their AS:
 
                                    Init    Conn    Hold    TCPSEG
Address            State     AS     Timer   Timer   Timer   Size
128.185.250.168    ENABLD    168    12      60      12      1024
192.0.251.165      ENABLD    165    12      60      12      1024
 
Receive-Policies:
Index  Type  Prefix       Mask      Match  OrgAS  AdjAS IGPmetric
1      INCL  0.0.0.0      0.0.0.0   Range  0      0      0
 
Send-Policies:
Index  Type  Prefix       Mask      Match  Tag    AdjAS
1      INCL  0.0.0.0      0.0.0.0   Range  0      0
 
Originate-Policies:
Index  Type  Prefix       Mask             Match  Tag
1      EXCL  194.10.16.0  255.255.240.0    Range  0
 
Aggregation:
 
Index  Prefix             Mask
1      194.10.16.0        255.255.240.0
No no-receive-AS records in configuration.

bgp speaker
Use the list bgp speaker command to derive information on the BGP speaker. The information provided is as follows:
Example:
list BGP speaker
BGP Protocol:          Enabled
AS:                    165
TCP-Segment Size:      1024

neighbor
Use the list neighbor command to derive information on BGP neighbors.

Example: list neighbor

Neighbors and their AS:
 
                                    Init    Conn    Hold    TCPSEG
Address            State     AS     Timer   Timer   Timer   Size
 
128.185.252.168    ENABLD    168    12      60      12      1024
192.0.190.178      DISBLD    178    12      60      12      1024
192.0.251.167      ENABLD    167    12      60      12      1024

no-receive
Use the list no-receive command to derive information on no-receive-AS definitions that have been added to the BGP configuration.

Example: list no-receive

AS-PATH with following autonomous systems will be discarded:
AS  178
AS  165

originate-policy all index prefix
Use the list originate-policy command to derive information on the originate policies that have been added to the BGP configuration.

Example: list originate-policy

Originate-Policies:
Index  Type  Prefix           Mask             Match  Tag
1      EXCL  194.10.16.0      255.255.240.0    Range  0
2      INCL  0.0.0.0          0.0.0.0          Range  0

policy-list
Use the list policy-list command to list configured policy-list names.

Example: list policy-list

BGP Config>li policy list
Policy list:
nbr1-rcv  Receive
nbr1-snd  Send

policy-to-neighbor
Use the list policy-to-neighbor command to list policies attached to neighbors.

Example: list policy-to-neighbor

Neighbor addrs  receive          send
192.0.251.165   nbr1-rcv         nbr1-snd
 

receive-policy adj-as-number all or index or prefix
Use the list receive-policy command to derive information on the receive policies that have been added to the BGP configuration. You can display all receive policies defined for an AS, or display policies by index or prefix number.

Example: list receive-policy

Receive-Policies:
Index  Type  Prefix      Mask        Match  OrgAS  AdjAS  IGPmetric
1      EXCL  0.0.0.0     0.0.0.0     Range  178    165
2      INCL  0.0.0.0     0.0.0.0     Range  0      0      0

send-policy adj-as-number all or index or prefix
Use the list send-policy command to display information on send policies defined for specified autonomous systems. You can display all send policies defined for an AS, or display policies by index or prefix number.

Example: list send-policy

Send-Policies:
Index  Type  Prefix      Mask           Match Tag    AdjAS
1      EXCL  194.10.16.0 255.255.240.0  Range   0    165
2      INCL   0.0.0.0    0.0.0.0        Range   0    0

Move

Use the move command to change the order in which policies and aggregates have been defined. This changes the order in which the router applies existing policies to route information. Before using this command, it is advisable to use the list command to see what policies have been defined.

Syntax:

move
aggregate or originate-policy or receive-policy or send-policy

Example:

move originate-policy
Enter index of originate-policy to move [1]? 3
Move record AFTER record number [0]?

Set

Use the set command to set the IP-route-table-scan-timer. The IP-route-table-scan-timer value is used to set the IP forwarding table scanning time interval for BGP updates.

Syntax:

set
ip-route-table-scan-timer
Example:
set ip-route-table-scan-timer   

Update

Use the update command and sub-commands to manipulate policies.

Syntax:

update
policy-list

Receive Policy Example:

update policy-list
Name[]? nbr1-rcv
    

Add

Use the Add command to add receive policies within the update command.

BGP nbr1-rcv: Receive Config>add
Policy type (Inclusive/Exclusive) [Exclusive]? inclusive
Network Prefix [0.0.0.0]?
Network Mask [0.0.0.0]?
Address Match (Exact/Range) [Range]?
Originating AS# [0]?
Any AS# [0]?
MED [0]?
Weight [0]?
Local-Pref [0]?
IGP-metric [0]?       
Note:There will be no prompting for MED, Local-pref, Weight, and IGP-metric parameters for exclusive receive policy. MED and Local-pref values will be used from received advertisement if they are configured as value '0'. The value '0' for the weight parameter indicates to ignore the weight value in the route selection process.

Change

Use the Change command to change policies within the update command.

Example:

Enter index of receive-policy to be modified [1]?

Delete

Use the delete command to delete policies within the update command.

Example:

Enter index of receive-policy to be deleted [1]?

Move

Use the move command to move policies within the update command.

Example:

Enter index of receive-policy to move [1]?
Move record after record number [0]?

List

Use the list policy-list command to list receive policies within the update command.

Example: list policy-list

Receive policy list for 'name':
                    T Prefix             Match OrgAS AnyAS MED   Weight Lpref IGPmetric
                1   I 0.0.0.0/0          Range 0     0     0     0      0     1

Send Policy Example:

update policy-list
Name[]? nbr1-rcv
    

Add

Use the Add command to add send policies within the update command.

BGP nbr1-rcv: Send Config>add
Policy type (Inclusive/Exclusive) [Exclusive]? inclusive
Network Prefix [0.0.0.0]?
Network Mask [0.0.0.0]?
Address Match (Exact/Range) [Range]?
Originating AS# [0]?
Any AS# [0]?
TAG [0]
MED [0]?
# of AS to pad[0]?       
Note:There will be no prompting for MED and ASpad parameters for exclusive send policy. The value 0 for the MED parameter indicates that MED attribute is not included in advertisement. The value 0 for the ASpad parameter indicates that there will be no additional local AS number inserted in the ASpath.

Change

Use the Change command to change policies within the update command.

Example:

Enter index of send-policy to be modified [1]?

Delete

Use the delete command to delete policies within the update command.

Example:

Enter index of send-policy to be deleted [1]?

Move

Use the move command to move policies within the update command.

Example:

Enter index of send-policy to move [1]?
Move record after record number [0]?

List

Use the list policy-list command to list send policies within the update command.

Example: list policy-list

Send policy list for 'name':
                    T Prefix             Match OrgAS AnyAS Tag   MED    ASpad
                1   I 0.0.0.0/0          Range 0     0     0     0      0     

Accessing the BGP Monitoring Environment

To access the BGP configuration environment, enter the following command at the Config> prompt:

  Config> Protocol BGP
  BGP>

BGP4 Monitoring Commands

This section describes the BGP monitoring commands. These commands allow you to modify the BGP protocol behavior to meet your specific requirements. Some amount of configuration is necessary to produce a fully functional BGP router. Enter BGP monitoring commands at the BGP> monitoring prompt.

Table 26. BGP Monitoring Command Summary
 Command   Function 
? (Help) Displays all the commands available for this command level or lists the options for specific commands (if available). See "Getting Help".
 Destinations   Displays all entries in the BGP routing table. 
 Disable neighbor   Disables a particular neighbor or all neighbors. 
 Dump routing tables   Lists the contents of the IP routing table. 
 Enable neighbor   Enables a particular neighbor or all neighbors. 
 Neighbors   Displays currently active neighbors. 
 Parameter   Displays installed BGP globals in the BGP system. 
 Paths   Displays all available paths in the database. 
 Ping   Sends ICMP Echo Requests to another host once a second and watch for a response. This command can be used to isolate trouble in an internetwork environment. 
 Policy-list   Displays the current installed policy for specific neighbor and usage statics of each policy. 
 Reset neighbor   Resets a particular neighbor. 
 Traceroute   Displays the complete path (hop-by-hop) to a particular destination. 
Exit Returns you to the previous command level. See "Exiting a Lower Level Environment".

Destinations

Use the destinations command to dump all BGP routing table entries, or to display information on routes advertised to, or received from, specified BGP neighbor addresses (destinations).

Syntax:

destinations
net address/net address net mask
advertised-to network address
received-from network address
Example: destination
            Network/MaskLen    NextHop         MED   Weight LPref AAG AGRAS ORG AS-Path
            142.4.0.0/16       192.0.251.165   100   0      0     No  0     IGP seq[165-178]

destinations net address
Displays detailed information on the specified route or destination network. The command shows how a specific route was learned, the best path to a specific destination, the metric associated with the route, and other information.

Example: destinations 142.4.0.0

Network/MaskLen   NextHop        MED  Weight LPref     AAG AGRAS ORG ASPath
142.4.0.0/16      192.0.251.165  100  0      0         No  0     IGP seq[165-178]
 
Dest:142.4.0.0/16, Age:180, Upd#:13,LastSent:0001:53:32 
 
Eligible paths: 2
PathID: 8  (Best Path)
        ASpath: seq[165-178]
        Origin: IGP, Pref: 507, LocalPref: 0
        Metric: 0, Weight: 0, MED: 100
        NextHop: 192.0.251.165, Neighbor: 192.0.251.165
        AtomicAggr: No
 
PathID: 21
        ASpath: seq[168-165-178]
        Origin: IGP, Pref: 505, LocalPref: 0
        Metric: 0, Weight: 0, MED: 0
        NextHop: 128.185.250.168, Neighbor: 128.185.250.168
        AtomicAggr: No

ASpath
Enumeration of autonomous systems along the path.

-seq:
Sequence of autonomous systems in order in the path

-set:
Set of autonomous systems in the path.

Origin
The originator of the destination. This is EGP, IGP, or Incomplete (originated by some other means not known).

LocalPref
The originating router's degree of preference for the destination.

Metric
The path metric with which the route is imported.

Weight
The path weight.

MED
A multi-exit discriminator value, used to discriminate among multiple entry/exit points to the same AS.

NextHop
The address of the router to use as the forwarding address for destinations reachable via the given path.

AtomicAggr
Indicates whether the router advertising the path has included the path in an atomic-aggregate.

destinations net address net mask
Displays detailed information on the specified route or destination network. The command shows how a specific route was learned, the best path to a specific destination, the metric associated with the route, and other information.

This command is useful in cases where multiple network addresses have the same prefix and different masks. In such cases, specifying the network mask narrows the scope of the information presented.

Example: destinations 194.10.16.0 255.255.240.0

Dest:194.10.16.0/21, Age:0, Upd#:3, LastSent:0002:00:00
 
Eligible paths: 1
PathID: 0 - (Best Path)
        ASpath:
        Origin: IGP, Pref: 0, LocalPref: 0
        Metric: 0, Weight: 0, MED: 0
        NextHop: 194.10.16.167, Neighbor: 194.10.16.167
        AtomicAggr: No, Aggregator AS167/194.10.16.167

destinations advertised-to net address
Lists all routes advertised to the specified BGP neighbor.

Example: destinations advertised-to

BGP neighbor address [0.0.0.0]? 192.0.251.165
 
        Destinations advertised to BGP neighbor 192.0.251.165
 
Network         NextHop         MED  Weight  LPref      AAG AGRAS ORG ASPath
194.10.16.0/20  194.10.16.167   0    0       0          No  167   IGP
192.0.190.0/24  192.0.251.165   0    0       0          No  0     IGP seq [165]
142.4.0.0/16    192.0.251.165   0    0       0          No  0     IGP seq [165-178]
143.116.0.0/16  128.185.250.168 0    0       0          No  0     IGP seq [168]

destinations received-from net address
Lists all routes received from the specified BGP neighbor.

Example: destinations received-from

BGP neighbor address [0.0.0.0]? 128.185.250.167
 
        Destinations obtained from BGP neighbor 128.185.250.167
 
Network              NextHop         MED Weight  LPref      AAG AGRAS ORG ASPath
194.10.16.0/20       128.185.250.167 0   0       0          No  167   IGP seq[167]
192.0.190.0/24       128.185.250.167 0   0       0          No  0     IGP seq[167-165]
142.4.0.0/16         128.185.250.167 0   0       0          No  0     IGP seq[167-165-178]

Disable Neighbor

Use the disable neighbor command to disable a particular neighbor or all neighbors that have been enabled. This command brings down the BGP session and removes the routes learned from that neighbor.

Syntax:

disable neighbor internet address

Example:
disable neighbor
Neighbor address (255.255.255.255 for all) [0.0.0.0]? 128.185.250.167

Dump Routing Tables

For a complete explanation of the dump routing tables command, refer to "Dump Routing Table" in the "Monitoring IP" chapter of Protocol Configuration and Monitoring Reference Volume 1

Enable Neighbor

Use the enable neighbor command to enable a particular neighbor or enable all neighbors that have been disabled. This command starts the BGP session with neighbor.

Syntax:

enable neighbor
internet address

Example:

Neighbor address (255.255.255.255 for all) [0.0.0.0]? 128.185.250.167

Neighbors

Use the neighbors command to display information on all active BGP neighbors.

Syntax:

neighbors
internet address

Example:
neighbors
IP-Address       Status   State        DAY-HH:MM:SS  BGPID           AS     Upd#
 
128.185.252.168  ENABLD  Established  00000:48:52  128.185.142.168  168     16
192.0.190.178    ENABLD  Established  00002:01:49  142.4.140.178    178     16
192.0.251.167    DISBLD  Established  00002:01:45  194.10.16.167    167     16

IP-Address
Specifies the IP address of the BGP neighbor.

State
Specifies the state of the connection. Possible states are:

Connect
Waiting for the TCP connection to the neighbor to be completed.

Active
In the event of TCP connection failure, the state is changed to Active, and the attempt to acquire the neighbor continues.

OpenSent
In this state OPEN has been sent, and BGP waits for an OPEN message from the neighbor.

OpenConfirm
In this state a KEEPALIVE has been sent in response to neighbor's OPEN, and waits for a KEEPALIVE/NOTIFICATION from the neighbor.

Established
A BGP connection has been successfully established, and can now start to exchange UPDATE messages.

BGP-ID
Specifies the neighbor's BGP Identification number.

AS
Specifies the neighbor's AS number.

Upd#
Specifies the sequence number of the last UPDATE message sent to the neighbor.

internet-address
Use the neighbor command to display detailed data on a particular BGP neighbor.

Example: neighbor 192.0.251.167

  Active Conn: Sprt:1026  Dprt:179    State: Established KeepAlive/Hold
  Time: 4/12
  Passve Conn: None
  TCP connection errors: 0          TCP state transitions: 0
 
  BGP Messages:     Sent       Received                     Sent
  Received
  Open:             1          1          Update:           11         11
  Notification:     0          0          KeepAlive:        1828       1830
  Total Messages:   1840       1842
 
  Msg Header Errs:  Sent       Received                     Sent
  Received
  Conn sync err:    0          0          Bad msg length:   0          0
  Bad msg type:     0          0
 
  Open Msg Errs:    Sent       Received                     Sent
  Received
  Unsupp versions:  0          0          Unsupp auth code: 0          0
  Bad peer AS ident:0          0          Auth failure:     0          0
  Bad BGP ident:    0          0          Bad hold time:    0          0
 
  Update Msg Errs:  Sent       Received                     Sent
  Received
  Bad attr list:    0          0          AS routing loop:  0          0
  Bad wlkn attr:    0          0          Bad NEXT_HOP atr: 0          0
  Mssng wlkn attr:  0          0          Optional atr err: 0          0
  Attr flags err:   0          0          Bad netwrk field: 0          0
  Attr length err:  0          0          Bad AS_PATH attr: 0          0
  Bad ORIGIN attr:  0          0
 
  Total Errors:     Sent       Received                     Sent
  Received
  Msg Header Errs:  0          0          Hold Timer Exprd: 0          0
  Open Msg Errs:    0          0          FSM Errs:         0          0
  Update Msg Errs:  0          0          Cease:            0          0

Parameter

Use the BGP parameter command to display installed BGP globals in the BGP system.

Syntax:

parameter

Example:

BGP> parameter 
 
classless-bgp is enabled.
compare-med-from-diff-as is enabled.
IP-route-table-scan-timer value is 5 seconds.

Paths

Use the BGP paths command to display the paths stored in the path description data base.

Syntax:

paths

Example:

paths
PathId   NextHop   MED  AAG   AGRAS  RefCnt   ORG   ASPath
0       10.2.0.3    0   No     0      2      IGP
4       192.2.0.2   0   No     0      2      IGP    seq[2]
5       192.2.0.2   0   No     2      1      IGP    seq[2]
6       192.2.0.2   0   No     0      1      IGP    seq[2-1]
7       10.2.0.168  0   No     0      4      IGP
8       192.3.0.1   0   No     0      2      IGP    seq[1]
9       192.2.0.2   0   No     2      1      IGP    seq[2]
10      10.2.0.3    0   No     0      1      IGP

PathId
Path identifier

NextHop
The address of the router to use as the forwarding address for the destinations that can be reached via the given path.

MED
The multi-exit discriminator used to discriminate among multiple entry/exit points to the same AS.

AAG
Indicates if the path has been atomic-aggregated that is the router that is advertising the given path has selected less specific route over the more specific one when presented with overlapping routes.

AGRAS
Indicates the AS number of the BGP speaker that aggregated the routes.

RefCnt
Indicates the number of path entities referring to the descriptor.

ORG
Specifies the originator of the advertised destinations in the given path: either EGP, IGP, or Incomplete (originated by some other means not known).

AS Path
Enumeration of autonomous systems along the path.

seq:
Sequence of autonomous systems in order in the path.

set:
Set of autonomous systems in the path.

Ping

For a complete explanation of the ping command, see the Ping command in the "Configuring and Monitoring IP" chapter in Protocol Configuration and Monitoring Reference Volume 1.

Policy-List

Use the policy-list command to display the current installed policy for specific neighbor and usage statistics of each policy.

Example: policy-list

Neighbor address[0.0.0.0]? 192.0.251.167
Policy Type(Receive/Send/Origin)[All]?Receive

Display for neighbor based policy configuration:

Receive policy list for neighbor '192.0.251.167': 
Idx T Prefix             Match OrgAS AnyAS MED   Weight LPref IGPmet Usage
1   I 0.0.0.0/0          Range 0     0     0     0      0     1      1

Display for AS based policy configuration:

Receive policy :
Idx Type  Prefix             Match OrgAS AdjAS IGPmetric Usage
1   INCL  0.0.0.0/0          Range 0     0     1         1

Example: policy-list

Neighbor address[0.0.0.0]? 192.0.251.167
Policy Type(Receive/Send/Origin)[All]?Send

Display for neighbor based policy configuration:

send policy list for neighbor '0.0.0.0': 192.0.251.167
Idx T Prefix             Match OrgAS AnyAS TAG   MED   ASpad Usage
1   I 0.0.0.0/0          Range 0     0     0     0     0     1
              

Display for AS based policy configuration

send policy :
Idx Type  Prefix             Match OrgAS AdjAS TAG   Usage
1   INCL  0.0.0.0/0          Range 0     0     0     1
              

Example: policy-list

Neighbor address[0.0.0.0]? 192.0.251.167
Policy Type(Receive/Send/Origin)[All]?Origin
 
Origin policy list for neighbor '0.0.0.0':
Idx T Prefix             Match TAG   Usage
1   I 0.0.0.0/0          Range 0     1

Reset Neighbor

Use the reset neighbor command to reset the specified BGP neighbor, based on the neighbor configuration parameters stored in the configuration memory.

Syntax:

reset neighbor internet address

Example:
reset neighbor
Neighbor address[0.0.0.0]? 128.185.250.167

Sizes

Use the BGP sizes command to display the number of entries stored in the various data bases.

Syntax:

sizes

Example:
sizes
# Paths:                                11
# Path descriptors:                      7
  Update sequence#:                     22
# Routing tbl entries (allocated):       6
# Current tbl entries (not imported):    0
# Current tbl entries (imported to IGP): 3

Paths
Total number of eligible paths for all the routes in the BGP routing table.

Path descriptors
Total number of path descriptors in the database used to hold common path information.

Update sequence#
Indicates the current update sequence number.

Routing tbl entries (allocated)
Indicates the number of entries in BGP routing table.

Current tbl entries (not imported)
Indicates the number of BGP routes not imported into IGP.

Current tbl entries(imported to IGP)
Indicates the number of BGP routes imported into IGP.

Traceroute

For a complete explanation of the traceroute command, refer to "Configuring and Monitoring IP" in Protocol Configuration and Monitoring Reference Volume 2.


[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]